导航菜单
首页 >  sIFR and DotNetNuke  > Current state of using sIFR and DNN

Current state of using sIFR and DNN

I didn't like sIFR at all in DNN.  It didn't give enough control over the final font size of the replacement, and often due to white space embedded within the font itself, it became seriously too small to read without setting the original no-sIFR font really huge.  I've used cufon and had much better luck with it.  It allows you to set the font size of the replacement font, just has better control.  And it doesn't require a user to have flash installed, it just requires javascript/jscript to work.  It integrated into dnn 5 with no problems.   The only limitation is that it will not work on menu items in dnn nav menu, probably not solpart either, since the menu is rendered using javascript and cufon and sIFR just couldn't touch it, I'm assuming because of the order of the javascript rendering or just the way the menus themselves are rendered.  The hard part is finding fonts that allow embedding on the web without some type of license that costs thousands of dollars, which I think is silly since you can use the same font in an image without that problem; it shouldn't matter how the font is rendered or delivered.  Anyway, the whole digital rights management will probably keep it fairly unpopular unless the totally free fonts available for commercial use expands to include fonts you'd actually want to use on your web page!  But, with the onset of css 3 that will bring with it cross-browser font embedding, maybe those options will open up and we'll have more choices in which fonts are available for embedding at no cost or a cost that is actually reasonable for not just huge corporations but the little guy, too...

JOHN GIESYDotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /yearDNN4Less.com Team DotNetNuke  

相关推荐: